The mobile app must remove temporary files when it terminates.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
SRG-APP-000516-MAPP-000065	SRG-APP-000516-MAPP-000065	SRG-APP-000516-MAPP-000065_rule		Medium

Description
Temporary files left on the system after an app has terminated may contain sensitive information. Such sensitive information includes authentication credentials or session identifiers that would enable an adversary to gain unauthorized access to other resources. Removing such files when an app terminates greatly mitigates the risk of this attack that would exploit these files and use them to re-launch the app, enjoy user privileges or breach the confidentiality or integrity of the data stored on the device.

Description

Temporary files left on the system after an app has terminated may contain sensitive information. Such sensitive information includes authentication credentials or session identifiers that would enable an adversary to gain unauthorized access to other resources. Removing such files when an app terminates greatly mitigates the risk of this attack that would exploit these files and use them to re-launch the app, enjoy user privileges or breach the confidentiality or integrity of the data stored on the device.

STIG	Date
Mobile Application Security Requirements Guide	2014-07-22

Details

Check Text ( C-SRG-APP-000516-MAPP-000065_chk )
Perform a dynamic program analysis by launching the app and checking to see if it stores any temporary files. Close the app. If any of these temporary files remain in persistent memory, this is a finding. If memory is not released and the app is not using garbage collection process for memory (e.g., Java Applications), this is a finding. Re-launch the app to perform selected actions that will knowingly generate temporary files. Exit the app, and then search for temporary files that are not being deleted by the app. If files generated during the app’s session were not deleted, this is a finding.

Check Text ( C-SRG-APP-000516-MAPP-000065_chk )

Perform a dynamic program analysis by launching the app and checking to see if it stores any temporary files. Close the app. If any of these temporary files remain in persistent memory, this is a finding. If memory is not released and the app is not using garbage collection process for memory (e.g., Java Applications), this is a finding. Re-launch the app to perform selected actions that will knowingly generate temporary files. Exit the app, and then search for temporary files that are not being deleted by the app. If files generated during the app’s session were not deleted, this is a finding.

Fix Text (F-SRG-APP-000516-MAPP-000065_fix)
Configure or code the mobile app to remove all temporary files before the application exits.